Media presentation effects

ABSTRACT

A user interface may present multiple presentation slides for user selection. Each slide may include one or more shapes, and a shape thread may be associated with each shape on the slide. For a selected slide, the user interface may present one or more shape threads associated with the selected slide. Each shape displayed on the selected slide may be associated with a particular shape thread, and a user may independently adjust one or more slide transition attributes of a shape via the associated shape thread.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Pat. Application Serial No. 16/785,845, filed Feb. 10, 2020, which is a continuation of U.S. Pat. Application Serial No. 14/464,607, filed Aug. 20, 2014 now U.S. Pat. No. 10,572,128, which is a continuation of PCT International Application No PCT/CN2013/084565, filed Sep. 29, 2013, the entire contents of which are incorporated herein by reference. A claim of priority, to the extent appropriate is made to each of the above-disclosed applications.

BACKGROUND

While presentation slides may provide a convenient and reusable authoring environment for presentation visuals, such slides may be used in a manner that is more appropriate for a document (e.g., large amounts of text, dense diagrams, and raw tabular data) than for speaker support. Presenting such material may be problematic for both the presenter and the audience. For example, excessive slide text may encourage the audience to read the slide rather than listen to the presenter. Further, abrupt transitions from one slide to another may result in a loss of visual context and may make the relationship between slide contents implicit. The presenter may prepare for a transition and make an appropriate verbal linkage. However, in the event that the presenter does not make such an explicit verbal connection, the audience may not be able to determine whether a logical connection exists between slides.

SUMMARY

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Some implementations provide techniques and arrangements for displaying a user interface that allows a user to create and manage shapes and shape transitions across multiple slides. In some examples, the user may select a slide via the user interface and one or more shape threads associated with the selected slide may be presented (e.g., via an effects pane). Each shape displayed on the selected slide may be associated with a shape thread, and the attributes of each shape may be independently definable via the associated shape threads.

In some implementations, different shapes transition at different rates in response to navigation between slides. In some cases, the user may independently vary a delay before each shape begins transitioning. To illustrate, an amount of time for one shape to transition between slides may be different from an amount of time for another shape to transition between slides. Further, in some implementations, semantic interpolation allows for transitions of non-continuous attributes (e.g., a year, a date, etc.) between slides.

BRIEF DESCRIPTION OF THE DRAWINGS

The Detailed Description is set forth with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different figures indicates similar or identical items or features.

FIGS. 1-20 illustrate a sequence of view of an example user interface for creating and managing presentation media effects, according to some implementations.

FIGS. 21-29 illustrate an example presentation of the media effects created and managed in the example user interface of FIGS. 1-20 , according to some implementations.

FIG. 30 illustrates an example process flow for creating and managing media effects, according to some implementations.

FIG. 31 illustrates an example process flow for presenting media effects, according to some implementations.

FIG. 32 illustrates an example system in which some implementations may operate.

DETAILED DESCRIPTION Overview

As discussed above, presentation slides may often be used in a manner that is more appropriate for a document than for supporting presenters. For example, excessive slide text and abrupt transitions between slides may be problematic for both the presenter and the audience. Presenters may attempt to enhance a presentation by animating transitions between slides or animating shapes on a particular slide. However, such incidental animation may not support the act of communication and may instead prove counterproductive by distracting or confusing the audience. While linear interpolation of object attributes between slides (e.g., “tweening” or “in-betweening”) may be possible, existing solutions do not allow for independent management of the attributes of each object individually. Rather, when transitioning between slides, existing solutions use linear interpolation over the same period of time for each object. Transitioning each object over the same period of time may prevent one object from transitioning at one speed and finishing the transition earlier, while another object transitions at another speed and finishes the transition later. Further, existing solutions do not provide for interpolation of non-continuous attributes (e.g., semantic attributes) between slides.

The present disclosure describes techniques and arrangements for creating and managing media effects to provide a more cinematic experience that may improve audience engagement by avoiding distracting incidental animation and allowing the presenter to control intra-slide and inter-slide animations and transitions. Some implementations include a user interface that may allow a user to independently control attributes of each individual shape within a slide as well as attributes of each individual shape between slides. Thus, the user interface may allow the user to manage individual shapes such that the shapes may evolve in a meaningful way during the presentation.

In some implementations, semantic attributes of a shape may be interpolated. As used herein, the term “semantic attribute” refers to a non-continuous attribute (e..g, alphabetical text or numerical values on a slide) in which at least an attribute context (e.g., whether the attribute represents a date, a time, a year, etc.) is used to determine how to properly interpolate attribute values between slides. By contrast, for a continuous attribute (e.g., position values, size values, or color values of an image), interpolation of attribute values between slides may be achieved based on an initial attribute value and a target attribute value without determining the context of the attribute. Semantic attributes may be interpolated between slides by, for example, presenting sequential values (e.g., 1, 2, 3, ... N; A, B, C, ...Z; etc.) of the semantic attributes over the interpolation period (i.e., between slides).

Example Implementations

FIGS. 1-20 illustrate examples of a user interface 100 that may be displayed via a computing device (e.g., on the display device 3208 of the computing device 3200 of FIG. 32 described below) and examples of user interaction with the user interface 100. The user interface 100 may allow a user to create and manage media effects, while potentially avoiding problems that may be associated with slide transitions and shape animations. FIG. 1 illustrates an example of the user interface 100 according to some implementations. In the example illustrated in FIG. 1 , the user interface 100 includes a preview pane 102, a detail view pane 104, and an effects pane 106.

The preview pane 102 may allow a user to select a particular slide to be presented in the detail view pane 104. FIG. 1 illustrates an example of a presentation that includes a first slide 108, a second slide 110, and a third slide 112. However, it will be appreciated that a presentation may include an alternative number of slides. For illustrative purposes only, a dashed line is shown around the second slide 110 in the preview pane 102 in order to indicate that the second slide 110 is the current slide that is displayed in the detail view pane 104. However, it will be appreciated that alternative methods of identifying the currently displayed slide (e.g., color, size, etc.) may also be used. Further, in some cases, the currently displayed slide (e.g., “Slide 2 of 3”) may be included in the preview pane 102 to assist the user in identifying the current location in the presentation. In some implementations, each slide in the preview pane 102 may include thumbnail images or other representations of the “shapes” that are displayed in more detail in the detail view pane 104. As used herein, the term “shape” may represent an object that includes an image, alphabetical text, numerical values, or video, among other alternatives.

The effects pane 106 may display “shape threads” corresponding to the particular slide that is currently displayed in the detail view pane 104. Each shape on each slide may be associated with a shape thread. As used herein, the term “shape thread” refers to the connection or path of shapes across slides. By connecting shapes across slides, a shape thread may allow the user to independently define an on-screen transition behavior of each shape individually. That is, the effects pane 106 allows a user to independently manage the behavior of each of the shapes within a particular slide (“intra-slide”) and between slides (“inter-slide”) via corresponding shape threads.

By creating a new slide for each step of an animated progression, the user may visualize the temporal changes in the user interface 100. This may create a high degree of inter-slide continuity, as shape animations or other transitions are not limited to a single slide. Further, the ability to individually manage the behavior of each shape within a particular slide may allow for a high degree of intra-slide continuity, as it may be desirable for each shape to behave differently within a particular slide.

In the example of FIG. 1 , the second slide 110 is currently displayed in the detail view pane 104. Accordingly, the effects pane 106 displays the shapes that are associated with the second slide 110. When building a presentation, the effects pane 106 may allow the user to view and edit shape threads across multiple (two or more) slides, preview the presentation from the currently displayed slide, and set slide-specific navigation and advancement options.

In the example of FIG. 1 , the second slide 110 includes a first shape 114 (e.g., a background image of a company logo for the “Acme” corporation). The effects pane 106 identifies a first shape thread 116 that is associated with the first shape 114. The second slide 110 also includes a second shape 118 (e.g., the alphabetical text “Import Debut”) that may be displayed in the foreground. That is, the second shape 118 may be displayed on top of the first shape 114. The effects pane 106 identifies a second shape thread 120 that is associated with the second shape 118. The second slide 110 further includes a third shape 122 (e.g., the numerical year “1955”) that may be displayed in the foreground. The effects pane 106 identifies a third shape thread 124 that is associated with the third shape 122.

In the example of FIG. 1 , the third shape 122 on the second slide 110 may correspond to a year (e.g., the year 1955) which may represent the target year from an initial year of 1937 (as illustrated in the preview pane 102 for the first slide 108). In this example, semantic interpolation may include an interpolation (e.g., a linear or non-liner transition) from the year 1937 to the year 1955 when transitioning between the first slide 108 and the second slide 110. As an illustrative example, in response to the user clicking the first slide 108 to advance to the second slide 110, the year may advance linearly (or non-linearly) from 1937 to 1955 during the slide transition (see e.g., FIGS. 24-26 described below). In some implementations, the transition is incremental. For example, the increment may be a default (e.g., increments of one year), may be explicitly set by the user, or may be inferred based on a number of slides between a first state and a target state, or an estimated time of presentation, among other alternatives.

The shape threads 116, 120, 124 displayed in the effects pane 106 may allow the user to customize a presentation such that shapes may evolve (i.e., move and/or change) in a meaningful way over time. To illustrate, a user may duplicate or copy and paste an existing slide to create a new slide, make changes to the new slide, and identify individual time periods over which various changes are to unfold when transitioning between slides. That is, for each slide in a presentation, the effects pane 106 may allow the user to identify independent time periods for each shape to reach a “target” or end state. To illustrate, the effects pane 106 identifies an endpoint of each shape and a relationship to a previous slide, while allowing shape transitions on different time scales.

A newly created shape may appear in the effects pane 106 with the “Appear” effect type (see e.g., FIG. 3 illustrating the creation of the first shape 114 on the first slide 108). A slide that is duplicated from the previous slide connects the corresponding shapes across slides and indicates in the effects pane 106 that the particular shape belongs to a shape thread that shows the “target” state change from the previous slide. Any changes made to the particular shape on the second slide 110 represent the result of automatic interpolation (e.g., “tweening” or “in-betweening”) of the state of the particular shape from the state on the first slide 108. For each shape, interpolation may occur over independent time periods that may be individually defined by the user in the effects pane 106 or may be defaults or inferred based on circumstances (e.g., previous slides, presentations, etc.).

In the example of FIG. 1 , each of the shape threads 116, 120, 124 identifies a location of each shape on the currently displayed slide. For example, the first shape 114 of the second slide 110 is illustrated in the first shape thread 116 as occupying most of the second slide 110 (e.g., a background image). Further, the second shape 118 is illustrated in the second shape thread 120 in the top right with a size that may be proportional to the size of the second shape 118, while the third shape 122 is illustrated in the third shape thread 124 in the top left with a size that may be proportional to the size of the third shape 122. Alternative methods of identifying the individual shapes in the effects pane 106 may also be used. For example, a number may be associated with a particular shape (e.g., the number one with the first shape 114, the number two with the second shape 118, and the number three with the third shape 122), and the same number may be used to identify the particular shape on each slide in which it appears.

In some implementations, linear interpolation is used for transitioning continuous attributes, such as spatial attributes, color-based attributes, font attributes, format attributes, or image attributes. For a continuous attribute, interpolation of attribute values between slides may be achieved based on an initial attribute value and a target attribute value without determining the context of the attribute. By contrast, for a non-continuous attribute (e.g., a semantic attribute), an attribute context (e.g., whether the attribute represents a date, a time, a year, etc.) be used to determine how to properly interpolate the non-continuous attribute values between slides. As an illustrative example of a continuous attribute, if an image appears on one slide at the top left (e.g., at position x1, y1) and appears on a subsequent slide at the bottom right (e.g., at position x2, y2), the spatial attributes (e.g., the relative positions) may be used to linearly transition the image between slides. That is, during a slide transition, the position of the image would linearly transition along an x-axis based on the difference between the x coordinates (e.g., x2 minus x1) and would linearly transition along a y-axis based on the difference between the y coordinates (e.g., y2 minus y1). By contrast, as an illustrative example of a non-continuous attribute, if first text (e.g., “January”) appears on one slide and second text (e.g., “December”) appears on another slide, the context of the text being a month may allow for the text to be properly interpolated during a slide transition. In this example, by identifying the text as a month, the text may transition from January to February, from February to March, etc. until reaching the target month of December.

In some implementations, continuous attribute interpolation is non-linear. As an illustrative example, an attribute value change may be slow initially, then speed up. Alternatively, the attribute value change may be fast initially, then slow down. As another illustrative example, the change may “ease” in multiple directions through an appropriately defined mathematical easing function. Such an easing function may be selected from a list of preset functions or may be constructed by a user (e.g., with a vertical axis representing a rate of change and a horizontal axis representing time). Further, negative rates of attribute value change may indicate “tweening” away from a target value in a way that could be used to create an overshooting effect before bouncing back. In some cases, an option (not shown in FIG. 1 ) may allow the user to sketch a non-linear motion path for a shape transition. This may simultaneously capture the intended easing function (e.g., by examining the timing of the sketched path). The path and the easing function may be automatically smoothed and later manipulated directly by the user.

With respect to continuous attributes, examples of spatial attributes may include width, height, x position, y position, left edge x position, right edge x position, top edge y position, bottom edge y position, or location and scale values from some other (e.g., polar) coordinate system. Examples of color-based attributes may include transparency, hue, saturation, brightness, alpha, red, green, blue, or some other color system. Examples of font attributes may include size, face, color, kerning, line spacing, or text effect (e.g., shadow angle, glow radius). Examples of format attributes may include fill color, line color, line weight, or shape effect (e.g., reflection depth, reflection separation). Examples of image attributes may include brightness, contrast, crop (each edge), among other alternatives.

In the example illustrated in FIG. 1 , the third shape thread 124 identifies other attributes of the third shape 122 that may be independently adjusted. For example, the additional independently adjustable shape attributes may include a width transition of the shape, a height transition of the shape, a horizontal transition of the shape, a vertical transition of the shape, a color transition of the shape, or a text transition of the shape, among other alternatives. In an example embodiment, independent adjustment of attributes allows the color of the text of the third shape 122 (i.e., “1955”) to change over one period of time, while the size of the third shape 122 changes over a different period of time.

FIG. 1 further illustrates a selectable semantic transition icon 126. As described further with respect to FIG. 19 and illustrated in FIGS. 24-26 , semantic transitions may include transitions associated with interpolation of “non-continuous” attributes such as alphabetical text or numerical values, among other alternatives. Semantic attributes may include numerical attributes, date and time attributes, typesetting attributes, or text attributes, among other alternatives. Examples of non-continuous numerical attributes may include a time interval (e.g., 1, 2, 3) or an ordinal (e.g., 1st, 2nd, 3^(rd)). Examples of date and time attributes may include a time (e.g., 21:15), a date (3Jan. 01, 1982), or a combination of date and time (e.g., 2008-08-08 8pm). An example of a text attribute may include words used, and semantic interpolation can include morphing one set of words into another by only blending out/in the differences between text strings.

As an illustrative example, selection of the semantic transition icon 126 may allow for a linear or non-linear (e.g., exponential) interpolation from the year 1937 in the first slide 108 to the year 1955 in the second slide 110. While FIG. 1 illustrates a year as an example of a non-continuous attribute, it will be appreciated that semantic transitions may also occur with respect to days of the week, months of the year, among other alternatives. Further, semantic transitions may include morphing text or images based on similarities. For example, the user may want to show several versions of different dates or places. Accordingly, invariate portions of text may be fixed while variable portions of the text may be smoothly blended in and out. As another illustrative example, semantic transitions may include gradually increasing or decreasing spacing between letters or numbers over a particular period of time. It will be appreciated that various other semantic transitions may be possible.

In some implementations, slides are set to advance to a non-consecutive slide, or to advance automatically after a specified time period to a specified slide. In some examples, a default slide transition option may be for the user to advance to the next slide by clicking on the current slide. However, as illustrated in FIG. 1 , a slide transition area 128 may allow the user to manually identify a time period after which the presentation automatically advances to another slide. As illustrated in the slide transition area 128 of FIG. 1 , the user may select to advance to a non-consecutive slide or to advance automatically after a specified time period to a specified slide.

The user interface 100 may also include a selectable Preview icon 130 to preview the presentation for the slide currently displayed in the detail view pane 104 (e.g., the second slide 110). Further, the user interface 100 may include a selectable Run icon 132 to begin the presentation, starting with the first slide 108.

FIGS. 2-20 illustrate examples of user interactions with the user interface 100 to create the presentation illustrated in FIG. 1 , while FIGS. 21-29 illustrate the presentation that is initiated in response to the user selecting the Run icon 132.

Referring to FIG. 2 , the user may add the first shape 114 to the first slide 108. As an illustrative non-limiting example, the user may identify an image to be added to the first slide 108 via a menu (not shown) that may be presented via the user interface 100. Further, in the illustrative example of FIG. 2 , the user may resize or otherwise manipulate the first shape 114 via a cursor.

In some cases, as illustrated in FIG. 2 , the first shape thread 116 may not appear in the effects pane 106 until after the user has added the first shape 114 to the first slide 108. FIG. 3 illustrates that the first shape thread 116 may be added to the effects pane 106 after the first shape 114 has been added to the first slide 108. FIG. 3 further illustrates that the “Type” of the first shape 114 is set to “Appear” as this is the first instance of the shape in the presentation. Further, as this is the first instance of the first shape 114 in the presentation, the “Over” time may represent the time period over which the first shape 114 appears on the first slide 108 after the initiation of the presentation. In the example of FIG. 3 , a default time to appear (e.g., zero seconds) may be associated with a new shape having the “Appear” type. That is, the first shape 114 may appear upon initiation of the presentation of the first slide 108. However, as described below, it will be appreciated that a default time to appear may be adjusted by the user.

Referring to FIG. 4 , in some implementations, the user copies the first slide 108 and pastes the first slide 108 in the preview pane 102 to create the second slide 110. Alternatively, the user may duplicate the slide (e.g., by selecting a duplication control). As shown in FIG. 4 , the second slide 110 includes the first shape 114, and the effects pane 106 identifies the first shape thread 116 as associated with the second slide 110.

FIG. 4 further illustrates that the “Type” of the first shape 114 on the second slide 110 is set to “Appear” in the effects pane 106. In this case, the “Over” time may represent the time period over which the first shape 114 transitions from the state on the previous slide (e.g., the first slide 108) to the state on the second slide 110 in response to the user advancing the second slide 110.

Referring to FIG. 5 , the user may copy the second slide 110 and paste the second slide 110 into the preview pane 102 or otherwise duplicate the second slide 110 to create the third slide 112. As shown in FIG. 5 , the third slide 112 includes the first shape 114, and the effects pane 106 identifies the first shape thread 116 as associated with the third slide 112.

FIG. 5 further illustrates that the “Type” of the first shape 114 is set to “Appear” on the third slide 112. The “Over” time may represent the time over which the first shape 114 transitions from the state on the previous slide (e.g., the second slide 110) in response to the user selecting to advance to the third slide 112.

FIG. 6 illustrates that the user may resize, reorient, or otherwise manipulate the first shape 114 on the third slide 112. FIG. 7 illustrates the result of the resizing of the first shape 114 on the third slide 112 in FIG. 6 . For example, as shown in the preview pane 102 and the detail view pane 104 of FIG. 7 , the first shape 114 has been enlarged and shifted down with respect to the second slide 110. FIG. 8 illustrates that the user may adjust the default time period for the first shape 114 to enter and transform as well as to transform and exit (e.g., from one second to one minute).

Referring to FIG. 9 , the user may select the second slide 110 in the preview pane 102 to display the second slide 110 in the detail view pane 104. The user may change the type of the first shape 114 to “Continuous” via the effects pane 106. For example, in the example of FIG. 9 , the user may select the “Continuous” type from a pull-down menu of different shape behavior types.

FIG. 10 illustrates that the user may select the first slide 108 to add another shape (e.g., the second shape 118) to the first slide 108, and FIG. 11 illustrates that the second shape 118 has been added to the first slide 108 and the second shape thread 120 has been added to the effects pane 106. FIG. 11 further illustrates that the type of the second shape 118 is set to “Appear” as this is the first instance of the second shape 118 in the presentation. The “Over” time may represent the time period for the second shape 118 to appear on the first slide 108 after the initiation of the presentation. That is, the user may define a delay before the second shape 118 is to be displayed on the first slide 108. FIG. 11 further illustrates that the user may adjust a default time period for the second shape 118 to appear (e.g., to three seconds). That is, as illustrated in the effects pane 106, the first shape 114 may be set to appear when the first slide 108 has been selected (e.g., after zero seconds), while the second shape 118 may be set to appear after a delay of three seconds. Thus, the user interface 100 may allow the user to independently manage the “intra-slide” visual effects (e.g., the time for a shape to appear on a particular slide) of each shape independently. FIGS. 21-23 described below illustrate that the first shape 114 (e.g., the company logo “Acme”) may appear before the second shape 118.

FIG. 12 illustrates that the user may add another shape (e.g., the third shape 122) to the first slide 108, and FIG. 13 illustrates that the third shape 122 has been added to the first slide 108 and the third shape thread 124 has been added to the effects pane 106. FIG. 13 further illustrates that the type of the third shape 122 is set to “Appear,” as this is the first instance of the third shape 122 in the presentation. The “Over” time may represent the time period for the third shape 122 to appear after the initiation of the presentation. That is, the user may define a delay before the third shape 122 is to be displayed on the first slide 108. FIG. 13 illustrates that the user may adjust the default time period for the third shape 122 to appear (e.g., to two seconds). That is, the first shape 114 may appear upon presentation of the first slide 108 (e.g., after zero seconds), the third shape 122 may appear after a delay of two seconds, and the second shape 118 may appear after a delay of three seconds. Thus, the user interface 100 may allow the user to better manage intra-slide continuity using different delay times for various shapes to appear on a particular slide. FIGS. 21-23 described below illustrate that the first shape 114 (e.g., the company logo “Acme”) may appear before the third shape 122 (e.g., upon initiation of the presentation), the third shape 122 (e.g., the year 1937) may appear after the first shape 114 (e.g., after two seconds), and the second shape 118 (e.g., the text “Founded”) may appear after the third shape 122 (e.g., after three seconds).

FIG. 14 illustrates one example of the user adding the second shape 118 to the second slide 110 by dragging and dropping the second shape 118 displayed in the detail view pane 104 for the first slide 108 onto the second slide 110 displayed in the preview pane 102. FIG. 15 illustrates that the second shape 118 has been added to the second slide 110 and the second shape thread 120 has been added to the effects pane 106 for the second slide 110. FIG. 15 further illustrates that the type of the second shape 118 is set to “Appear” on the second slide 110. The “Over” time may represent the time over which one or more attribute values of the second shape 118 transition from the associated attribute values on a previous slide (e.g., the first slide 108) upon the user advancing to the second slide 110.

FIG. 15 further illustrates that the user may edit the text of the second shape 118 from “Founded” to “Import Debut,” and FIG. 16 illustrates the updated text in the detail view pane 104 and the preview pane 102 for the second slide 110. FIG. 16 further illustrates that the user may adjust the default time period for the second shape 118 to appear (e.g., to two seconds).

FIG. 17 illustrates one example of the user adding the third shape 122 to the second slide 110 by dragging and dropping the third shape 122 displayed in the detail view pane 104 for the first slide 108 onto the second slide 110 displayed in the preview pane 102. FIG. 18 illustrates that the third shape 122 has been added to the second slide 110 and the third shape thread 124 has been added to the effects pane 106 for the second slide 110. FIG. 18 further illustrates that the type of the third shape 122 is set to “Appear.” The “Over” time may represent the time period over which one or more attribute values of the third shape 122 transition from the associated attribute values on the previous slide (e.g., the first slide 108) upon the user advancing to the second slide 110.

FIG. 18 further illustrates that the user may edit the numerical year of the third shape 122 from “1937” to “1955,” and FIG. 19 illustrates the updated year in the detail view pane 104 and the preview pane 102 for the second slide 110. FIG. 19 further illustrates that the user may adjust the default time period for the third shape 122 to appear on the second slide 110 (e.g., to three seconds). In some implementations, the second shape 118 and the third shape 122 disappear at the same time upon advancing from the second slide 110 to the third slide 112. However, FIGS. 28 and 29 described below illustrate that the second shape 118 (e.g., “Import Debut”) and the third shape 122 (e.g., “1955”) may disappear at different times upon transitioning from the second slide 110 to the third slide 112. For example, the second shape 118 may disappear after two seconds, while the third shape 122 may disappear after three seconds. Thus, the user interface 100 may allow the user to independently manage not only the time for each shape to appear but also the time for each shape to disappear.

FIG. 19 further illustrates that the user may select the semantic attribute icon 126. For example, FIGS. 23-26 described below illustrate an example of semantic interpolation in which the third shape 122 interpolates from the year 1937 to the year 1955 as the presentation transitions from the first slide 108 to the second slide 110. Further, FIGS. 23-26 illustrate that the second shape 118 transitions from “Founded” to “Import Debut” while the presentation transitions from the first slide 108 to the second slide 110.

FIG. 20 illustrates that the user may select the Run icon 132 to initiate the presentation, and FIG. 21 illustrates the first slide 108 of the presentation after the first shape 114 has appeared. FIG. 21 illustrates that the size and position of the first shape 114 (e.g., the company logo “Acme”) corresponds to the initial size and position of the first shape 114 on the first slide 108. As the type of the first shape 114 is set to “Continuous,” the size and position of the first shape 114 may gradually transition (e.g., over a period of one minute, as defined by the user in FIG. 8 ) from the initial state on the first slide 108 to the target state on the third slide 112. This gradual transition may occur independently of any user action with respect to the presentation. That is, the user may remain on a particular slide for a period of time that is appropriate for the delivery of the presentation, while the background image of the “Acme” company logo may transition independently over the user-defined time period (e.g., over a time period of one minute in this example). This independent transition may improve inter-slide continuity.

FIG. 22 illustrates that the third shape 122 (e.g., the year 1937) may appear on the first slide 108 after the first shape 114. For example, as described with respect to FIG. 13 , the user may define the time for the third shape 122 to appear on the first slide 108 as two seconds. FIG. 23 illustrates that the second shape 118 (e.g., the text “Founded”) may appear on the first slide 108 after the third shape 122. For example, as described with respect to FIG. 11 , the user may define the time for the second shape 118 to appear on the first slide 108 as three seconds. Thus, FIGS. 21-23 illustrate the intra-slide behavior of the shapes 114, 118, and 122 on the first slide 108 as defined by the user in the user interface 100.

Referring to FIG. 23 , the user may click on the first slide 108 or otherwise select to transition from the first slide 108 to the second slide 110. FIG. 24 illustrates an example of the transition from the first slide 108 to the second slide 110 in accordance with the shape threads 116, 120, and 124 as defined by the user via the user interface 100.

Referring to FIG. 24 , the second shape 118 and the third shape 122 begin transitioning to the target state corresponding to the second slide 110. For example, the second shape 118 begins transitioning from the text “Founded” in first slide 108 to the text “Import Debut” in the second slide 110 over a time period of two seconds (as defined by the user in FIG. 13 ). FIG. 24 illustrates one example of the transition with the text “Founded” fading out while the text “Import Debut” fades in. FIG. 24 further illustrates that the third shape 122 begins the semantic transition from the year 1937 in the first slide 108 to the year 1955 in the second slide 110 over a time period of three seconds (as defined by the user in FIG. 11 ). In FIG. 24 , the year 1939 is illustrated as the value for the third shape 122, representing a semantic transition of two years from the initial year of 1937 on the first slide 108 to the target year of 1955 on the second slide 110. However, it will be appreciated that this is for illustrative purposes only.

FIG. 25 illustrates a continuation of the transition of the second shape 118 and the third shape 122. In FIG. 25 , the second shape 118 continues transitioning from the text “Founded” to the text “Import Debut,” while the third shape 122 continues the semantic transition from the year 1937 to the year 1955. In FIG. 25 , the year 1949 is illustrated as the value for the third shape 122, representing a semantic transition of ten years from the year 1939 in FIG. 24 . However, it will be appreciated that this is for illustrative purposes only.

FIG. 26 illustrates the second slide 110 upon completion of the transition. That is, the second shape 118 has completed the transition from the text “Founded” to the text “Import Debut,” while the third shape 122 has completed the semantic transition to the year 1955.

FIGS. 21-26 further illustrate that the first shape 114 with a “Continuous” effect type continues the interpolation from the initial state on the first slide 108 to the target state on the third slide 112 over the time period of one minute as specified by the user (as illustrated in FIG. 11 ), independent of the actions of the presenter during the presentation. Referring to FIG. 27 , the size and position of the first shape 114 has further changed with respect to the size and position of the first shape 114 in FIG. 26 . The degree of size and position transition may correspond to an amount of time between the completion of the transition in FIG. 26 and the presenter clicking on the second slide 110 in FIG. 27 to advance to the third slide 112. In the event that the amount of time that has elapsed between the initial appearance of the first shape 114 on the first slide 108 has reached the time specified for the first shape 114 to complete the transition to the target state on the third slide 112 (e.g., one minute), the transition of size and position of the first shape 114 may end at the target state identified in the third slide 112, even though the presenter has not yet reached the third slide 112.

In some implementations, the second shape 118 and the third shape 122 disappear at the same time when advancing to the third slide 112. However, FIGS. 28 and 29 illustrate an alternative transition from the second slide 110 to the third slide 112 in response to the user advancing from the second slide 110 to the third slide 112 (e.g., by clicking on the second slide 110 in FIG. 27 ). FIGS. 28 and 29 illustrate an example in which the second shape 118 (e.g., “Import Debut”) and the third shape 122 (e.g., the year “1955”) disappear at different times during the transition from the second slide 110 to the third slide 112. For example, the second shape 118 may disappear after two seconds, while the third shape 122 may disappear after three seconds as illustrated in FIG. 29 .

FIGS. 30 and 31 illustrate example process flows according to some implementations. In the flow diagrams of FIGS. 30 and 31 , each block represents one or more operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, cause the processors to perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, modules, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the blocks are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes. Numerous other variations will be apparent to those of skill in the art in light of the disclosure herein. For discussion purposes, the process flows in FIGS. 30 and 31 are described with reference to FIGS. 1-29 , described above, although other models, frameworks, systems and environments may implement the illustrated process.

Referring to FIG. 30 , at block 3002, the process flow 3000 includes creating a slide. For example, referring to FIG. 2 , the user may create the first slide 108 via the user interface 100. As illustrated in FIG. 2 , the first slide 108 may be displayed in the preview pane 102 and the detail view pane 104 of the user interface 100.

At block 3004, the process flow 3000 optionally includes setting slide actions. For example, referring to FIG. 2 , the user may optionally manually identify a time period after which the presentation automatically advances to another slide.

At block 3006, the process flow 3000 includes adding a shape to the slide. For example, referring to FIGS. 2 and 3 , the user may add the first shape 114 to the first slide 108. As illustrated in FIG. 3 , after adding the first shape 114 to the first slide 108 in FIG. 2 , the first shape 114 is displayed in the detail view pane 104, and a thumbnail image of the first shape 114 may be displayed in the preview pane 102. Further, FIG. 3 illustrates that the first shape thread 116 associated with the first shape 114 is added to the effects pane 106 for the first slide 108.

At block 3008, the process flow 3000 includes duplicating the slide. For example, referring to FIG. 4 , the user may duplicate the first slide 108 to create the second slide 110. After duplicating the slide at block 3008, the process flow 3000 may return to block 3006, and a shape may be added to the duplicate slide. For example, referring to FIGS. 14 and 15 , the second shape 118 may be added to the second slide 110 by dragging and dropping the second shape 118 from the first slide 108 displayed in the detail view pane 104 to the second slide 110 (e.g., the duplicate slide) displayed in the preview pane 102. As another example, referring to FIGS. 17 and 18 , the third shape 122 may be added to the second slide 110 by dragging and dropping the third shape 122 from the first slide 108 displayed in the detail view pane 104 to the second slide 110 (e.g., the duplicate slide) displayed in the preview pane 102.

At block 3010, the process flow 3000 includes creating a shape thread with the “Appear” effect type. For example, referring to FIG. 3 , the first shape thread 116 may be created in the effects pane 106 in response to the user adding the first shape 114 to the first slide 108. As another example, referring to FIGS. 10 and 11 , the second shape thread 120 may be created in the effects pane 106 in response to the user adding the second shape 118 to the first slide 108. As a further example, referring to FIGS. 12 and 13 , the third shape thread 124 may be created in the effects pane 106 in response to the user adding the third shape 122 to the first slide 108.

At block 3012, for the duplicate slide created at block 3008, the process flow 3000 includes extending a shape thread with the “Target” effect type. For example, referring to FIGS. 14 and 15 , the second shape thread 120 associated with the second shape 118 may be extended to the second slide 110, and the second shape thread 120 may be displayed in the effects pane 106 for the second slide 110. As another example, referring to FIGS. 17 and 18 , the third shape thread 124 associated with the third shape 122 may be extended to the second slide 110, and the third shape thread 124 may be displayed in the effects pane 106 for the second slide 110.

At block 3014, the process flow 3000 optionally includes connecting the shape thread with the “Reappear” effect type. While not illustrated in FIGS. 1-20 , it will be appreciated that one or more of the shape threads 116, 120, 124 may be set to “Reappear” in a subsequent slide. As an illustrative example, if a fourth slide were to be added after the third slide 112, one or more of the shape threads 120 or 124 that were set to disappear upon transitioning from the second slide 110 to the third slide 112 may be set to reappear on the fourth slide.

At block 3016, the process flow 3000 includes editing one or more shapes (e.g., shapes on either the slide created at block 3002 or the duplicate slide created at block 3008). To illustrate, referring to FIGS. 6 and 7 , the user may edit the first shape 114 on the third slide 114 to resize and reorient the first shape 114. As another example, referring to FIGS. 15 and 16 , the user may edit the second shape 118 on the second slide 110 (e.g., to replace the text “Founded” with the text “Import Debut”). As a further example, referring to FIGS. 18 and 19 , the user may edit the third shape 122 on the second slide 110 (e.g., to replace the year “1937” with the year “1955”).

At block 3018, the process flow 3000 optionally includes setting the effect timing (e.g., from a default timing value). For example, referring to FIG. 11 , the user may change the default timing for the appearance of the second shape 118 on the first slide 108 from one second to three seconds. As another example, referring to FIG. 13 , the user may change the default timing for the appearance of the third shape 122 on the first slide 108 from one second to two seconds. FIGS. 21-23 illustrate that this change of appearance timing results in the first shape 114 being the first shape to appear on the first slide 108, the third shape 122 appearing next (e.g., after two seconds), and the second shape 118 appearing next (e.g., after three seconds).

As another example, the user may change the effect timing for the duplicate slide created at block 2008 (e.g., the second slide 110). For example, referring to FIG. 16 , the user may change the default timing for the transition of the second shape 118 from one second to two seconds. As another example, referring to FIG. 19 , the user may change the default timing for the transition of the third shape 122 from one second to three seconds. FIGS. 24-26 illustrate that this change of appearance timing results in the second shape 118 transitioning from the first slide 108 to the second slide 110 over a time period of two seconds, and the third shape 122 transitioning to the second slide 110 over a time period of three seconds).

At block 3020, the process flow 3000 includes unlinking shapes with the effect type “Appear” or one or more attributes with the effect type “Continuous.” For example, referring to FIG. 9 , the user may change the effect type of the first shape 114 on the second slide 110 to “Continuous.”

Referring to FIG. 31 , at block 3102, the process flow 3100 includes beginning a presentation. For example, referring to FIG. 20 , the user may begin the presentation by clicking the Run icon 132, while FIG. 21 illustrates the first slide 108 of the presentation being displayed in response.

At block 3104, the process flow 3100 includes starting a presentation timer. At block 3106, the process flow 3100 optionally includes setting a current state to that of the slide preceding the selected slide. At block 3108, the process flow 3100 includes saving the current state. At block 3110, the process flow 3100 includes setting the target slide to the selected slide. At block 3112, the process flow 3100 includes interpolating shape attributes over the specified time towards those of their next target slide.

To illustrate, referring to FIG. 8 , the user may specify that the first shape 114 is set to reach its target state as defined on the third slide 112 after one minute. As illustrated in FIGS. 21-29 , the size and position of the first shape 114 may be interpolated from the initial size and position on the first slide 108 to the target size and position on the third slide 112 over the time period of one minute specified by the user.

At block 3116, the process flow 3100 includes advancing to the next or another slide. For example, referring to FIGS. 23 and 24 , the user may click or otherwise select to advance from the first slide 108 to the second slide 110. In response, the first slide 108 transitions to the second slide 110 as illustrated in FIGS. 24-26 in accordance with the parameters specified by the user in the user interface 100. As another example, referring to FIGS. 27 and 28 , the user may click or otherwise select to advance from the second slide 110 to the third slide 112. FIGS. 28 and 29 illustrate a particular example of the second slide 110 transitioning to the third slide 112.

The process flows 3000 and 3100 illustrated in FIGS. 30 and 31 are merely example process flows. In other examples, the operations/blocks may be rearranged, combined, modified, or omitted without departing from the disclosure.

Example Computing Device and Environment

FIG. 32 illustrates an example configuration of a computing device 3200 and an environment that can be used to implement the modules and functions described herein. It should be understood that the computing device 3200 may be configured in a similar manner to that illustrated.

The computing device 3200 may include at least one processor 3202, a memory 3204, communication interfaces 3206, a display device 3208 (e.g. a touchscreen display), other input/output (I/O) devices 3210 (e.g. a touchscreen display or a mouse and keyboard), and one or more mass storage devices 3212, able to communicate with each other, such as via a system bus 3214 or other suitable connection.

The processor 3202 may be a single processing unit or a number of processing units, all of which may include single or multiple computing units or multiple cores. The processor 3202 can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions. Among other capabilities, the processor 3202 can be configured to fetch and execute computer-readable instructions stored in the memory 3204, mass storage devices 3212, or other computer-readable media.

Memory 3204 and mass storage devices 3212 are examples of computer storage media for storing instructions which are executed by the processor 3202 to perform the various functions described above. For example, memory 3204 may generally include both volatile memory and non-volatile memory (e.g., RAM, ROM, or the like). Further, mass storage devices 3212 may generally include hard disk drives, solid-state drives, removable media, including external and removable drives, memory cards, flash memory, floppy disks, optical disks (e.g., CD, DVD), a storage array, a network attached storage, a storage area network, or the like. Both memory 3204 and mass storage devices 3212 may be collectively referred to as memory or computer storage media herein, and may be computer-readable media capable of storing computer-readable, processor-executable program instructions as computer program code that can be executed by the processor 3202 as a particular machine configured for carrying out the operations and functions described in the implementations herein.

The computing device 3200 may also include one or more communication interfaces 3206 for exchanging data with other devices, such as via a network, direct connection, or the like, as discussed above. The communication interfaces 3206 can facilitate communications within a wide variety of networks and protocol types, including wired networks (e.g., LAN, cable, etc.) and wireless networks (e.g., WLAN, cellular, satellite, etc.), the Internet and the like. Communication interfaces 3206 can also provide communication with external storage (not shown), such as in a storage array, network attached storage, storage area network, or the like.

The discussion herein refers to data being sent and received by particular components or modules. This should not be taken as a limitation as such communication need not be direct and the particular components or module need not necessarily be a single functional unit. This is not to be taken as limiting implementations to only those in which the components directly send and receive data from one another. The signals could instead be relayed by a separate component upon receipt of the data. Further, the components may be combined or the functionality may be separated amongst components in various manners not limited to those discussed above. Other variations in the logical and practical structure and framework of various implementations would be apparent to one of ordinary skill in the art in view of the disclosure provided herein.

A display device 3208, such as touchscreen display or other display device, may be included in some implementations. The display device 3208 may be configured to display the user interface 100 as described above. Other I/O devices 3210 may be devices that receive various inputs from a user and provide various outputs to the user, and may include a touchscreen, such as a touchscreen display, a keyboard, a remote controller, a mouse, a printer, audio input/output devices, and so forth.

Memory 3204 may include modules and components for execution by the computing device 3200 according to the implementations discussed herein. Memory 3204 may further include one or more other modules 3216, such as an operating system, drivers, application software, communication software, or the like. Memory 3204 may also include other data 3218, such as data stored while performing the functions described above and data used by the other modules 3216. Memory 3204 may also include other data and data structures described or alluded to herein.

The example systems and computing devices described herein are merely examples suitable for some implementations and are not intended to suggest any limitation as to the scope of use or functionality of the environments, architectures and frameworks that can implement the processes, components and features described herein. Thus, implementations herein are operational with numerous environments or architectures, and may be implemented in general purpose and special-purpose computing systems, or other devices having processing capability. Generally, any of the functions described with reference to the figures can be implemented using software, hardware (e.g., fixed logic circuitry) or a combination of these implementations. The term “module,” “mechanism” or “component” as used herein generally represents software, hardware, or a combination of software and hardware that can be configured to implement prescribed functions. For instance, in the case of a software implementation, the term “module,” “mechanism” or “component” can represent program code (and/or declarative-type instructions) that performs specified tasks or operations when executed on a processing device or devices (e.g., CPUs or processors). The program code can be stored in one or more computer-readable memory devices or other computer storage devices. Thus, the processes, components and modules described herein may be implemented by a computer program product.

As used herein, “computer-readable media” includes computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory or other memory technology, compact disk ROM (CD-ROM), digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store information for access by a computing device.

In contrast, communication media may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave. As defined herein, computer storage media does not include communication media.

Furthermore, this disclosure provides various example implementations, as described and as illustrated in the drawings. However, this disclosure is not limited to the implementations described and illustrated herein, but can extend to other implementations, as would be known or as would become known to those skilled in the art. Reference in the specification to “one implementation,” “this implementation,” “these implementations” or “some implementations” means that a particular feature, structure, or characteristic described is included in at least one implementation, and the appearances of these phrases in various places in the specification are not necessarily all referring to the same implementation.

Conclusion

Although the subject matter has been described in language specific to structural features and/or methodological acts, the subject matter defined in the appended claims is not limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims. This disclosure is intended to cover any and all adaptations or variations of the disclosed implementations, and the following claims should not be construed to be limited to the specific implementations disclosed in the specification. Instead, the scope of this document is to be determined entirely by the following claims, along with the full range of equivalents to which such claims are entitled. 

1-20. (canceled)
 21. A system comprising: at least one processor; and memory storing instructions that, when executed by the at least one processor, causes the system to perform operations comprising: determining a first semantic attribute value for a shape on a first document page; determining a second semantic attribute value for the shape on a second document page; determining an attribute context for interpolating between the first semantic attribute value and the second semantic attribute value, wherein the attribute context represents a non-numeric attribute; generating, based on the attribute context, an interpolated semantic attribute value for the shape; and presenting the shape according to the interpolated semantic attribute value while transitioning between the first document page and the second document page, wherein the interpolated semantic attribute value is presented as an intermediate semantic value between the first semantic attribute value and the second semantic attribute value.
 22. The system of claim 21, wherein the first document page and the second document page are each a slide of a presentation document.
 23. The system of claim 21, wherein the non-numeric attribute relates to a list of terms or phrases arranged in a predefined order.
 24. The system of claim 21, wherein the non-numeric attribute relates to a range of alphabetical text values.
 25. The system of claim 21, wherein the interpolated semantic attribute value transitions the first semantic attribute value to the second semantic attribute value by at least one of: adding one or more words to the first semantic attribute value; or removing one or more words from the first semantic attribute value.
 26. The system of claim 21, wherein the interpolated semantic attribute value is presented as at least one of blending in or blending out differences between the first semantic attribute value and the second semantic attribute value.
 27. The system of claim 21, wherein the interpolated semantic attribute value represents a linear transition from the first semantic attribute value to the second semantic attribute value.
 28. The system of claim 21, wherein the interpolated semantic attribute value represents a non-linear transition from the first semantic attribute value to the second semantic attribute value.
 29. The system of claim 21, wherein the first semantic attribute value and the second semantic attribute value are presented via a user interface comprising a preview pane, a detail view pane, and an effects pane.
 30. The system of claim 29, wherein: the detail view pane is used to present and interact with the first document page and the second document page; and the preview pane includes a preview of the first document page and the second document page such that changes made to the first document page and the second document page in the detail view pane or reflected in the preview pane.
 31. The system of claim 30, wherein the effects pane comprises one or more shape threads for controlling a connection or path of shapes across document pages.
 32. The system of claim 31, wherein the one or more shape threads enable a user to define an on-screen transition behavior of the shapes.
 33. The system of claim 31, wherein the one or more shape threads enable a user to define an amount of time over which the shapes appear on the document pages.
 34. The system of claim 31, wherein the one or more shape threads enable a user to define a location of the shapes on the document pages.
 35. A method comprising: determining a first semantic attribute value for a shape on a first slide; determining a second semantic attribute value for the shape on a second slide; determining an attribute context for interpolating between the first semantic attribute value and the second semantic attribute value, wherein the attribute context represents a set of alphabetical text values; generating, based on the attribute context, an interpolated semantic attribute value for the shape; and presenting the shape according to the interpolated semantic attribute value while transitioning between the first slide and the second slide, wherein the interpolated semantic attribute value is presented as an intermediate semantic value that is within a range boundary of the first semantic attribute value and the second semantic attribute value.
 36. The method of claim 35, wherein the set of alphabetical text values is arranged according to a position of each of the set of alphabetical text values within a list.
 37. The method of claim 35, wherein the interpolated semantic attribute value represents a middle value between the range boundary of the first semantic attribute value and the second semantic attribute value.
 38. A system comprising: at least one processor; and memory storing instructions that, when executed by the at least one processor, causes the system to perform operations comprising: determining a first image attribute value for a shape on a first document page; determining a second image attribute value for the shape on a second document page; generating an interpolated image attribute value for the shape; and presenting the shape according to the interpolated image attribute value while transitioning between the first document page and the second document page, wherein the interpolated image attribute value is presented as an intermediate image value between the first image attribute value and the second image attribute value.
 39. The system of claim 38, wherein the first image attribute value for the shape is a color.
 40. The system of claim 38, wherein the first image attribute value for the shape is at least one of: brightness; contrast; or a cropping of the shape. 